Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0c5c3f217210e029ae8c3fe729c24ce7db677aa67a5a3021119e22540c37a4b

Tx prefix hash: 236489b5601f0673452897f9b8150f026143f2f2330ebbe3178f8fddee03cdf2
Tx public key: 209a561c58ce2f235a3210892221f1afb65e0cfc66ef57d633ff2442ddcd6cd4
Timestamp: 1724352861 Timestamp [UCT]: 2024-08-22 18:54:21 Age [y:d:h:m:s]: 00:279:20:34:53
Block: 1093652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199914 RingCT/type: yes/0
Extra: 01209a561c58ce2f235a3210892221f1afb65e0cfc66ef57d633ff2442ddcd6cd4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25b48ffb143e377dc4ebcbcfb34691afd3c2b78e69fd3dcdb702cb5c4aacc0f8 0.600000000000 1568639 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": 1093662, "vin": [ { "gen": { "height": 1093652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25b48ffb143e377dc4ebcbcfb34691afd3c2b78e69fd3dcdb702cb5c4aacc0f8" } } ], "extra": [ 1, 32, 154, 86, 28, 88, 206, 47, 35, 90, 50, 16, 137, 34, 33, 241, 175, 182, 94, 12, 252, 102, 239, 87, 214, 51, 255, 36, 66, 221, 205, 108, 212, 2, 17, 0, 0, 0, 3, 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