Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54ccfe93093a6098a1684c15d1c4a9aee6c528fd53911050b956bcff68ea1457

Tx prefix hash: 5c1606125220129d6f6bb8187dd9957111e3d28454a507f5fe262a9e0c21cc66
Tx public key: 0146e475f9aeb613f560f242efd6c6589b29859e57ff2a6756ca452f8db99399
Timestamp: 1759230889 Timestamp [UCT]: 2025-09-30 11:14:49 Age [y:d:h:m:s]: 00:049:01:50:37
Block: 1379679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35140 RingCT/type: yes/0
Extra: 010146e475f9aeb613f560f242efd6c6589b29859e57ff2a6756ca452f8db99399021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ab8b2d70d0e5106b53dc2d30bbfd991260bc52b4e62f9fca1f2892592f6d4f8 0.600000000000 1867786 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": 1379689, "vin": [ { "gen": { "height": 1379679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ab8b2d70d0e5106b53dc2d30bbfd991260bc52b4e62f9fca1f2892592f6d4f8" } } ], "extra": [ 1, 1, 70, 228, 117, 249, 174, 182, 19, 245, 96, 242, 66, 239, 214, 198, 88, 155, 41, 133, 158, 87, 255, 42, 103, 86, 202, 69, 47, 141, 185, 147, 153, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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