Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77bc323cdf9652c1632ceb0c5682508c8869db600c0b1da8d2b7c85ed803bba1

Tx prefix hash: 5b162bb84413ba45d85c7fbe6f8b3f2f3da9bb02cf0d2279d271557268656573
Tx public key: 7b1bc702ef926aeac6d9b0176e5de90e97923f5503556cee7ee52f8e084171b8
Timestamp: 1744408109 Timestamp [UCT]: 2025-04-11 21:48:29 Age [y:d:h:m:s]: 00:212:18:20:31
Block: 1259415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149782 RingCT/type: yes/0
Extra: 017b1bc702ef926aeac6d9b0176e5de90e97923f5503556cee7ee52f8e084171b802110000000cdbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd41c2d3b4b0522dda5e8e8852d77245ccc814d411d2dc631608f372751a4a38 0.600000000000 1746554 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": 1259425, "vin": [ { "gen": { "height": 1259415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd41c2d3b4b0522dda5e8e8852d77245ccc814d411d2dc631608f372751a4a38" } } ], "extra": [ 1, 123, 27, 199, 2, 239, 146, 106, 234, 198, 217, 176, 23, 110, 93, 233, 14, 151, 146, 63, 85, 3, 85, 108, 238, 126, 229, 47, 142, 8, 65, 113, 184, 2, 17, 0, 0, 0, 12, 219, 181, 113, 193, 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