Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a53cd621cd4151f168ff0695b30beeeb8dc3dc6d03ef07170a34d20340bd8341

Tx prefix hash: 2ecedc77f2ef17d56c43c0e3694f1b109fddbc60194c95f37e76926de85d3901
Tx public key: 398d4e0d019a76c03e15a4b48183722f2bcddaf4a80943038d00f2d4fd94cd1b
Timestamp: 1726495345 Timestamp [UCT]: 2024-09-16 14:02:25 Age [y:d:h:m:s]: 00:075:17:15:44
Block: 1111406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54148 RingCT/type: yes/0
Extra: 01398d4e0d019a76c03e15a4b48183722f2bcddaf4a80943038d00f2d4fd94cd1b021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97ee0f0193d7414aa8a8cb8440b1cc2dd0276022d64cc09ac0807ef189922fa1 0.600000000000 1590355 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": 1111416, "vin": [ { "gen": { "height": 1111406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97ee0f0193d7414aa8a8cb8440b1cc2dd0276022d64cc09ac0807ef189922fa1" } } ], "extra": [ 1, 57, 141, 78, 13, 1, 154, 118, 192, 62, 21, 164, 180, 129, 131, 114, 47, 43, 205, 218, 244, 168, 9, 67, 3, 141, 0, 242, 212, 253, 148, 205, 27, 2, 17, 0, 0, 0, 17, 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