Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fe5b1edd6f12cb287c72e9ba388c158834ac0cb256c75d10a6e233ffd887f1c

Tx prefix hash: 674f773e009eeac88d7dabdafb37e871b43a6d30a05d7aed9ececeaf77743dac
Tx public key: dcdff0a4d51b584245f112512cfe398aafc4d0b4bb716d1209164a8cb6c877bc
Timestamp: 1727144946 Timestamp [UCT]: 2024-09-24 02:29:06 Age [y:d:h:m:s]: 00:197:16:02:35
Block: 1116792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141083 RingCT/type: yes/0
Extra: 01dcdff0a4d51b584245f112512cfe398aafc4d0b4bb716d1209164a8cb6c877bc021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ebcbac74663cc193184b0395312b9be242b8d71611d4c85305bce25337c3332 0.600000000000 1597399 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": 1116802, "vin": [ { "gen": { "height": 1116792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ebcbac74663cc193184b0395312b9be242b8d71611d4c85305bce25337c3332" } } ], "extra": [ 1, 220, 223, 240, 164, 213, 27, 88, 66, 69, 241, 18, 81, 44, 254, 57, 138, 175, 196, 208, 180, 187, 113, 109, 18, 9, 22, 74, 140, 182, 200, 119, 188, 2, 17, 0, 0, 0, 8, 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