Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 647161eb6dccc1f6deba83c4ab5497d17c0e546d0a80afbed3e477d37578f4f9

Tx prefix hash: b368b711601f1661817c5aeb69c9812c3774965bf287bbc9b4cf69c43669e4a0
Tx public key: 7de9db287dc62d70002ae05f14f8112fdcda39754c017343273b9e1efa8bd693
Timestamp: 1727425884 Timestamp [UCT]: 2024-09-27 08:31:24 Age [y:d:h:m:s]: 01:042:09:07:48
Block: 1119129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288671 RingCT/type: yes/0
Extra: 017de9db287dc62d70002ae05f14f8112fdcda39754c017343273b9e1efa8bd69302110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce5d4bb0160e775374b38e8c9c5c9e8bfb6d7f83bf57e9e7ac5529e33fe64246 0.600000000000 1600570 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": 1119139, "vin": [ { "gen": { "height": 1119129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce5d4bb0160e775374b38e8c9c5c9e8bfb6d7f83bf57e9e7ac5529e33fe64246" } } ], "extra": [ 1, 125, 233, 219, 40, 125, 198, 45, 112, 0, 42, 224, 95, 20, 248, 17, 47, 220, 218, 57, 117, 76, 1, 115, 67, 39, 59, 158, 30, 250, 139, 214, 147, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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