Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72d662c1e1bcb8df513e50798fa99767e060c780f7e75eb4d96184aa6a0ae543

Tx prefix hash: 1ccadbf1048eed20e6ab1c2d39728277c96300fed288bc81eb5d72ee0d62dd9b
Tx public key: bfb5897d83c8fcb84a4a2e821a3dd4c8d4a0846b951a9b2b13efa7d2ae655215
Timestamp: 1736906457 Timestamp [UCT]: 2025-01-15 02:00:57 Age [y:d:h:m:s]: 00:154:15:10:15
Block: 1197563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110229 RingCT/type: yes/0
Extra: 01bfb5897d83c8fcb84a4a2e821a3dd4c8d4a0846b951a9b2b13efa7d2ae655215021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1a9eeaec4dda7d7fa7eaed6bc4f678ced5dd8f1c9474f8599da7ee0c1056092 0.600000000000 1684176 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": 1197573, "vin": [ { "gen": { "height": 1197563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1a9eeaec4dda7d7fa7eaed6bc4f678ced5dd8f1c9474f8599da7ee0c1056092" } } ], "extra": [ 1, 191, 181, 137, 125, 131, 200, 252, 184, 74, 74, 46, 130, 26, 61, 212, 200, 212, 160, 132, 107, 149, 26, 155, 43, 19, 239, 167, 210, 174, 101, 82, 21, 2, 17, 0, 0, 0, 4, 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