Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9990d614c5bc1f8940aa4f8204005f55967c7f1c0920cec007473f646135c646

Tx prefix hash: 73025c1bcdf9cf8c6cddd656e9c4ae0be9b41ee29051567a8338f5cc16090189
Tx public key: 537dd6403023e7108f3b4d7753688881f6d3d0d0c2dfb099e7072b04d3411b35
Timestamp: 1726386739 Timestamp [UCT]: 2024-09-15 07:52:19 Age [y:d:h:m:s]: 00:182:21:06:09
Block: 1110506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130534 RingCT/type: yes/0
Extra: 01537dd6403023e7108f3b4d7753688881f6d3d0d0c2dfb099e7072b04d3411b35021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cb7e3acbfd0268f39db0c808b2994d7ba741c9a66758ec148a094a211443214 0.600000000000 1589137 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": 1110516, "vin": [ { "gen": { "height": 1110506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cb7e3acbfd0268f39db0c808b2994d7ba741c9a66758ec148a094a211443214" } } ], "extra": [ 1, 83, 125, 214, 64, 48, 35, 231, 16, 143, 59, 77, 119, 83, 104, 136, 129, 246, 211, 208, 208, 194, 223, 176, 153, 231, 7, 43, 4, 211, 65, 27, 53, 2, 17, 0, 0, 0, 4, 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