Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 769b51feda8c38dca2ceb44bd8235b1f1abfc2216ff39d7ec581cc129dbc8d65

Tx prefix hash: d459baa8b9aad6c47e79005c22b68dc6f053e254150ea7885ee54de89b114092
Tx public key: ed86d03830f1feb3f802157797a60fb5f6a354e5be05ac19796dd2936240d907
Timestamp: 1728707455 Timestamp [UCT]: 2024-10-12 04:30:55 Age [y:d:h:m:s]: 00:206:17:19:31
Block: 1129760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147531 RingCT/type: yes/0
Extra: 01ed86d03830f1feb3f802157797a60fb5f6a354e5be05ac19796dd2936240d907021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9ff11c274e37faf39d57331e9a23d21c81d5d29af8e0ed366f3a214916ad227 0.600000000000 1612613 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": 1129770, "vin": [ { "gen": { "height": 1129760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9ff11c274e37faf39d57331e9a23d21c81d5d29af8e0ed366f3a214916ad227" } } ], "extra": [ 1, 237, 134, 208, 56, 48, 241, 254, 179, 248, 2, 21, 119, 151, 166, 15, 181, 246, 163, 84, 229, 190, 5, 172, 25, 121, 109, 210, 147, 98, 64, 217, 7, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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