Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49779c0a9bd17879e90e5d5af5a69141dbadaabef457d5a0ec74f573ea6fbeb9

Tx prefix hash: a927c8a5bfdafae1be5f1ec9e82a6a60578e1e487825ff2ef396e60f3f02a267
Tx public key: 5fc9ae5ed5a8e5ea05071abdee78013ae5e1b4f4f571e8569e54a8a2f2f8b2a1
Timestamp: 1719454495 Timestamp [UCT]: 2024-06-27 02:14:55 Age [y:d:h:m:s]: 00:263:10:16:42
Block: 1053022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188247 RingCT/type: yes/0
Extra: 015fc9ae5ed5a8e5ea05071abdee78013ae5e1b4f4f571e8569e54a8a2f2f8b2a10211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19ac73898869572d15d287f0ba5f7eca9c444322ed6065919cc4eb1143ad65e1 0.600000000000 1523367 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": 1053032, "vin": [ { "gen": { "height": 1053022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19ac73898869572d15d287f0ba5f7eca9c444322ed6065919cc4eb1143ad65e1" } } ], "extra": [ 1, 95, 201, 174, 94, 213, 168, 229, 234, 5, 7, 26, 189, 238, 120, 1, 58, 229, 225, 180, 244, 245, 113, 232, 86, 158, 84, 168, 162, 242, 248, 178, 161, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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