Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e7483b418a2d85d67c04a2334e8e70c85432d81851359ecf680b7fb762a19bc

Tx prefix hash: 0837141472d66819e73ef1b678964117aa20700f8d07e7ad16d2f8c1827624ad
Tx public key: 349991bf005d18cb2410a3e618bbdb29b774f2f5617a0f08dc70e4768e42a01e
Timestamp: 1735542923 Timestamp [UCT]: 2024-12-30 07:15:23 Age [y:d:h:m:s]: 00:109:23:27:58
Block: 1186275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78399 RingCT/type: yes/0
Extra: 01349991bf005d18cb2410a3e618bbdb29b774f2f5617a0f08dc70e4768e42a01e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb2b58c3901e4a107245eccc6c263b4ac2e2afa3a6823106e8fab6e41cd29c0b 0.600000000000 1672754 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": 1186285, "vin": [ { "gen": { "height": 1186275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb2b58c3901e4a107245eccc6c263b4ac2e2afa3a6823106e8fab6e41cd29c0b" } } ], "extra": [ 1, 52, 153, 145, 191, 0, 93, 24, 203, 36, 16, 163, 230, 24, 187, 219, 41, 183, 116, 242, 245, 97, 122, 15, 8, 220, 112, 228, 118, 142, 66, 160, 30, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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