Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3b3b926af1c38c197f199d51c0f7c5fd3bbb68632ee90d534fb5989cc750c22

Tx prefix hash: 9cd02f1e4ca4ec156ce5f62b8159d596369e30583f8bec071424180a0e6e0fb2
Tx public key: 327bb5de68c567001324da2c37d32405a22565de4ff1e0666d85a42396964300
Timestamp: 1726482577 Timestamp [UCT]: 2024-09-16 10:29:37 Age [y:d:h:m:s]: 00:182:00:52:42
Block: 1111294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129948 RingCT/type: yes/0
Extra: 01327bb5de68c567001324da2c37d32405a22565de4ff1e0666d85a42396964300021100000003e914dd15000000000000000000

1 output(s) for total of 0.608020000000 dcy

stealth address amount amount idx
00: cc4e8e736532fd0cf0e08d81fd5062f4a2848b9519591e277b20873d09377681 0.608020000000 1590201 of 0

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": 1111304, "vin": [ { "gen": { "height": 1111294 } } ], "vout": [ { "amount": 608020000, "target": { "key": "cc4e8e736532fd0cf0e08d81fd5062f4a2848b9519591e277b20873d09377681" } } ], "extra": [ 1, 50, 123, 181, 222, 104, 197, 103, 0, 19, 36, 218, 44, 55, 211, 36, 5, 162, 37, 101, 222, 79, 241, 224, 102, 109, 133, 164, 35, 150, 150, 67, 0, 2, 17, 0, 0, 0, 3, 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