Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 955cbc74662193bb814c7118b6a232043b35290ba8a4c5b64beff116e122c7c3

Tx prefix hash: 04142cb15f2f7154a18fe635c620ecc21b4335b486f49e1214ec942c0967003a
Tx public key: 23159d511a143e47e3698b15288d7826c6b4448c1b901e86ceccaa5b576408ea
Timestamp: 1583029434 Timestamp [UCT]: 2020-03-01 02:23:54 Age [y:d:h:m:s]: 04:271:06:23:57
Block: 74417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087592 RingCT/type: yes/0
Extra: 0123159d511a143e47e3698b15288d7826c6b4448c1b901e86ceccaa5b576408ea02110000005812c4732d000000000000000000

1 output(s) for total of 347.877535867000 dcy

stealth address amount amount idx
00: 039f70ad2ecb2f36441ab1b2fe7bdcbdd4813383f5a96b2c25d0b8d5c5eb2074 347.877535867000 137727 of 0

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": 74427, "vin": [ { "gen": { "height": 74417 } } ], "vout": [ { "amount": 347877535867, "target": { "key": "039f70ad2ecb2f36441ab1b2fe7bdcbdd4813383f5a96b2c25d0b8d5c5eb2074" } } ], "extra": [ 1, 35, 21, 157, 81, 26, 20, 62, 71, 227, 105, 139, 21, 40, 141, 120, 38, 198, 180, 68, 140, 27, 144, 30, 134, 206, 204, 170, 91, 87, 100, 8, 234, 2, 17, 0, 0, 0, 88, 18, 196, 115, 45, 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