Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6b984f1dc7cb00c975ea872396696ec90e0742aebb260dd1bf85cea33a57908

Tx prefix hash: 4bebb741fe39524a5a3b3691474233d69c52dd512fedc98394d7d41bc2990c19
Tx public key: d585cc7be97840c246bdde4cb9ae615481a6dc3c97e00a5e495e2ece72e82be6
Timestamp: 1741208175 Timestamp [UCT]: 2025-03-05 20:56:15 Age [y:d:h:m:s]: 00:257:02:52:28
Block: 1232920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181508 RingCT/type: yes/0
Extra: 01d585cc7be97840c246bdde4cb9ae615481a6dc3c97e00a5e495e2ece72e82be60211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6867b7461190224ddcb84cdd9ee656eb1d26b8281d79120b9205a4984f9ae0a 0.600000000000 1719837 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": 1232930, "vin": [ { "gen": { "height": 1232920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6867b7461190224ddcb84cdd9ee656eb1d26b8281d79120b9205a4984f9ae0a" } } ], "extra": [ 1, 213, 133, 204, 123, 233, 120, 64, 194, 70, 189, 222, 76, 185, 174, 97, 84, 129, 166, 220, 60, 151, 224, 10, 94, 73, 94, 46, 206, 114, 232, 43, 230, 2, 17, 0, 0, 0, 6, 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