Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cddcf8bd3dfad8be38d7b6d028b6b1dbfc58034f87d7a2fdbcd12bbf360a820c

Tx prefix hash: 0d60f0faa5a7d73a9626bf75c932e48f7bae81cdc4a7811400a35d0d33fc4e01
Tx public key: 003aa14659d4955e116d2fcca4608cc194a2d999994181d491e9a8dddddbd291
Timestamp: 1722847641 Timestamp [UCT]: 2024-08-05 08:47:21 Age [y:d:h:m:s]: 00:196:14:39:14
Block: 1081157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140364 RingCT/type: yes/0
Extra: 01003aa14659d4955e116d2fcca4608cc194a2d999994181d491e9a8dddddbd291021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9974150b341243806bdc1c3fd2559acf3c2754244d5dff91aabb3a59219e8e4 0.600000000000 1554796 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": 1081167, "vin": [ { "gen": { "height": 1081157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9974150b341243806bdc1c3fd2559acf3c2754244d5dff91aabb3a59219e8e4" } } ], "extra": [ 1, 0, 58, 161, 70, 89, 212, 149, 94, 17, 109, 47, 204, 164, 96, 140, 193, 148, 162, 217, 153, 153, 65, 129, 212, 145, 233, 168, 221, 221, 219, 210, 145, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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