Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74a0a246e00038c0065bf72517673a4c6224ba54b83b6bb1246a69630324a456

Tx prefix hash: 4350828cf62c5510701a237d408c28ec7d96c4b919e129564a3bd15745ec34b1
Tx public key: 41e8846f8f38e2125a2da6856c0dc2f1c2a555b4ab1679fb31a6b48f6eaeb11f
Timestamp: 1708419858 Timestamp [UCT]: 2024-02-20 09:04:18 Age [y:d:h:m:s]: 01:322:21:56:06
Block: 961554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489615 RingCT/type: yes/0
Extra: 0141e8846f8f38e2125a2da6856c0dc2f1c2a555b4ab1679fb31a6b48f6eaeb11f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 115d19a21e23c213d3242c3d78c938456805565c5218bc8d97a096915d92548b 0.600000000000 1421165 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": 961564, "vin": [ { "gen": { "height": 961554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "115d19a21e23c213d3242c3d78c938456805565c5218bc8d97a096915d92548b" } } ], "extra": [ 1, 65, 232, 132, 111, 143, 56, 226, 18, 90, 45, 166, 133, 108, 13, 194, 241, 194, 165, 85, 180, 171, 22, 121, 251, 49, 166, 180, 143, 110, 174, 177, 31, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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