Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25584e8f0c6b3b18d39f9a19bd8d1b53695f0a07596e84f47ad06840735c4762

Tx prefix hash: fb2a44d4645e4c41e5fc317270154b62911fb10bf6f4aff9ce9e4dd258bd4335
Tx public key: d51952d48b94f7200139188b2bb78a7d04928b88d7bccda8f770552351e58ca5
Timestamp: 1730456468 Timestamp [UCT]: 2024-11-01 10:21:08 Age [y:d:h:m:s]: 00:022:21:35:25
Block: 1144151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16399 RingCT/type: yes/0
Extra: 01d51952d48b94f7200139188b2bb78a7d04928b88d7bccda8f770552351e58ca50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d1721b28ea3fbff1bd4aa487bb42b3ddf2f4579e094dcbfe3aca35cf65f9b9d 0.600000000000 1628270 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": 1144161, "vin": [ { "gen": { "height": 1144151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d1721b28ea3fbff1bd4aa487bb42b3ddf2f4579e094dcbfe3aca35cf65f9b9d" } } ], "extra": [ 1, 213, 25, 82, 212, 139, 148, 247, 32, 1, 57, 24, 139, 43, 183, 138, 125, 4, 146, 139, 136, 215, 188, 205, 168, 247, 112, 85, 35, 81, 229, 140, 165, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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