Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b900c8142ad2185e14df9ad71cf8803af14fcd77e8af18b4f62548cdd3807770

Tx prefix hash: 453435714bb305e33f4d21094696c79b4fc64bb6da894a996b81cae70c6e219e
Tx public key: c0b976e0b2f4deef9e88df5c1853667fb59d4a99059681648a03951b250c8612
Timestamp: 1726298470 Timestamp [UCT]: 2024-09-14 07:21:10 Age [y:d:h:m:s]: 00:215:12:04:14
Block: 1109768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153849 RingCT/type: yes/0
Extra: 01c0b976e0b2f4deef9e88df5c1853667fb59d4a99059681648a03951b250c8612021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcf9fd948758d08020a5c7a291c89c51142dc77eb7513b84aa8f5e65bb646873 0.600000000000 1588139 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": 1109778, "vin": [ { "gen": { "height": 1109768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcf9fd948758d08020a5c7a291c89c51142dc77eb7513b84aa8f5e65bb646873" } } ], "extra": [ 1, 192, 185, 118, 224, 178, 244, 222, 239, 158, 136, 223, 92, 24, 83, 102, 127, 181, 157, 74, 153, 5, 150, 129, 100, 138, 3, 149, 27, 37, 12, 134, 18, 2, 17, 0, 0, 0, 7, 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