Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4548e79f11d08db0ba8845badb50db1fdcec8a5dc7b51c1a52e496c72def5ca

Tx prefix hash: 6e20c83c5766f4212d8cfdc3afbec4188a68ea6ae87bd94f1552b3c71b6f8c0b
Tx public key: a96b683d1af4e9617296c6f24908648b18aa09de63e3ebdf75c8439504735e34
Timestamp: 1734005299 Timestamp [UCT]: 2024-12-12 12:08:19 Age [y:d:h:m:s]: 00:108:19:29:24
Block: 1173583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77532 RingCT/type: yes/0
Extra: 01a96b683d1af4e9617296c6f24908648b18aa09de63e3ebdf75c8439504735e34021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea52fc972137084d92b179db37b11eb7485a090b10b00a3cc7d402fea9ce21cf 0.600000000000 1659622 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": 1173593, "vin": [ { "gen": { "height": 1173583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea52fc972137084d92b179db37b11eb7485a090b10b00a3cc7d402fea9ce21cf" } } ], "extra": [ 1, 169, 107, 104, 61, 26, 244, 233, 97, 114, 150, 198, 242, 73, 8, 100, 139, 24, 170, 9, 222, 99, 227, 235, 223, 117, 200, 67, 149, 4, 115, 94, 52, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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