Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f7bd8784ffd733054746d25e1f0483e486bf34a2fcdf7278c810455915c2cd99

Tx prefix hash: cbaffe9009b8d9ae838574e8e51de4e82c6d33ea719d3b203b3fa85896643334
Tx public key: db70efe5990ce913eef6daeb6f072ae2f029aa4053c2f4cc78dd70e7043c6949
Timestamp: 1714187309 Timestamp [UCT]: 2024-04-27 03:08:29 Age [y:d:h:m:s]: 00:348:22:52:41
Block: 1009354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249462 RingCT/type: yes/0
Extra: 01db70efe5990ce913eef6daeb6f072ae2f029aa4053c2f4cc78dd70e7043c69490211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae6f55fc24c6a6ec1bf86ef5089b82cfdc33a0ceb6c927bd515e61352fcc359e 0.600000000000 1471004 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1009364, "vin": [ { "gen": { "height": 1009354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae6f55fc24c6a6ec1bf86ef5089b82cfdc33a0ceb6c927bd515e61352fcc359e" } } ], "extra": [ 1, 219, 112, 239, 229, 153, 12, 233, 19, 238, 246, 218, 235, 111, 7, 42, 226, 240, 41, 170, 64, 83, 194, 244, 204, 120, 221, 112, 231, 4, 60, 105, 73, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8