Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b609b3548e7d58e9965bb9973c742c90071718cd8da04e0202a18b18dc0ce68a

Tx prefix hash: 347dbb1591ca3ac33b8ec71aa81b2b0d6af5f90932af4efb8fe04ac41bdb027e
Tx public key: b035b9e0b48e9daa8bb7c62d1005157cd4ffd5de00235c223936dee0391c7f64
Timestamp: 1736558079 Timestamp [UCT]: 2025-01-11 01:14:39 Age [y:d:h:m:s]: 00:066:02:21:41
Block: 1194685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47024 RingCT/type: yes/0
Extra: 01b035b9e0b48e9daa8bb7c62d1005157cd4ffd5de00235c223936dee0391c7f64021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c929ede09c0c1296ccab5606558403e01221c1450ae790fd03d93e6f17c4e623 0.600000000000 1681262 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": 1194695, "vin": [ { "gen": { "height": 1194685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c929ede09c0c1296ccab5606558403e01221c1450ae790fd03d93e6f17c4e623" } } ], "extra": [ 1, 176, 53, 185, 224, 180, 142, 157, 170, 139, 183, 198, 45, 16, 5, 21, 124, 212, 255, 213, 222, 0, 35, 92, 34, 57, 54, 222, 224, 57, 28, 127, 100, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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