Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55f8583fef79aa20b147834809c8b47312813f2712e616cc2333d569587e97bf

Tx prefix hash: 1199749f9ec3db4acd078609c1c9510ae19d33f4a3e9aff9b322ef8852f8410d
Tx public key: 9e57d7376e423da14687b0dad7f4cd68268eef3a90b03db1f86d85e2b3e2de5c
Timestamp: 1745374178 Timestamp [UCT]: 2025-04-23 02:09:38 Age [y:d:h:m:s]: 00:261:15:14:08
Block: 1267401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184791 RingCT/type: yes/0
Extra: 019e57d7376e423da14687b0dad7f4cd68268eef3a90b03db1f86d85e2b3e2de5c02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ae63ddf21f6b4d0558acf49a0f31ba328349c1c3c5c68835eb41f62fbc11269 0.600000000000 1754630 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": 1267411, "vin": [ { "gen": { "height": 1267401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ae63ddf21f6b4d0558acf49a0f31ba328349c1c3c5c68835eb41f62fbc11269" } } ], "extra": [ 1, 158, 87, 215, 55, 110, 66, 61, 161, 70, 135, 176, 218, 215, 244, 205, 104, 38, 142, 239, 58, 144, 176, 61, 177, 248, 109, 133, 226, 179, 226, 222, 92, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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