Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31c672195fe6a8642ef74efa27803e6bffd4c51457cf0083d11ed556aa08e4cd

Tx prefix hash: a62758a49ffa4b32a0eb4ee304b1cd62d38a41be7cf3244b10f45ad516f9b75d
Tx public key: f767d76690e78316d8dadccab144549b1c0c49c85b4dacf7f0a30b2e2a33d21a
Timestamp: 1736530434 Timestamp [UCT]: 2025-01-10 17:33:54 Age [y:d:h:m:s]: 00:314:03:45:02
Block: 1194464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222034 RingCT/type: yes/0
Extra: 01f767d76690e78316d8dadccab144549b1c0c49c85b4dacf7f0a30b2e2a33d21a0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7c0c56287d8a35da482a727dc97f678f35f71bebe165ef93d37f3464904b7e2 0.600000000000 1681035 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": 1194474, "vin": [ { "gen": { "height": 1194464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7c0c56287d8a35da482a727dc97f678f35f71bebe165ef93d37f3464904b7e2" } } ], "extra": [ 1, 247, 103, 215, 102, 144, 231, 131, 22, 216, 218, 220, 202, 177, 68, 84, 155, 28, 12, 73, 200, 91, 77, 172, 247, 240, 163, 11, 46, 42, 51, 210, 26, 2, 17, 0, 0, 0, 7, 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