Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b51310f935642cdc6be0e299fa2e7c9cb8b7b6f3549d1c0cbac1ae5f66ea1a0

Tx prefix hash: 3f2bd40dac1a567ade6bad5a2c55fb37d3ca727fb149fe7d75bd87f951e1cc09
Tx public key: d7fb2d322f5cdf0c536aaefb8e39729d5850153ff59fdcf270c3de35a43826e5
Timestamp: 1657106914 Timestamp [UCT]: 2022-07-06 11:28:34 Age [y:d:h:m:s]: 03:117:12:11:50
Block: 537836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 863717 RingCT/type: yes/0
Extra: 01d7fb2d322f5cdf0c536aaefb8e39729d5850153ff59fdcf270c3de35a43826e5021100000017a8c141c5000000000000000000

1 output(s) for total of 10.137391424000 dcy

stealth address amount amount idx
00: 0e888f891d833d01bdc65976e0815efd0ab3eee916425595baa3f9888d4caf48 10.137391424000 967767 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": 537846, "vin": [ { "gen": { "height": 537836 } } ], "vout": [ { "amount": 10137391424, "target": { "key": "0e888f891d833d01bdc65976e0815efd0ab3eee916425595baa3f9888d4caf48" } } ], "extra": [ 1, 215, 251, 45, 50, 47, 92, 223, 12, 83, 106, 174, 251, 142, 57, 114, 157, 88, 80, 21, 63, 245, 159, 220, 242, 112, 195, 222, 53, 164, 56, 38, 229, 2, 17, 0, 0, 0, 23, 168, 193, 65, 197, 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