Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f453a7357c0721fb3cf3fdfe0c06ed66f3401d98416f5567e7900b335ddd84be

Tx prefix hash: d04228e9aa6e9630435de34345a4d440e57c414db1fed9ba74b2742062f40f03
Tx public key: 353ee8acda7145b4e87b21bcd908d5e37e5ea3d2dfba15c35a2ca8fc195220b7
Timestamp: 1699623646 Timestamp [UCT]: 2023-11-10 13:40:46 Age [y:d:h:m:s]: 01:152:18:55:48
Block: 888633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370386 RingCT/type: yes/0
Extra: 01353ee8acda7145b4e87b21bcd908d5e37e5ea3d2dfba15c35a2ca8fc195220b702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.697573513000 dcy

stealth address amount amount idx
00: 57209de11350f99a54387ea1cad779c00153a98d40a145c946a69f9800148d80 0.697573513000 1344586 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": 888643, "vin": [ { "gen": { "height": 888633 } } ], "vout": [ { "amount": 697573513, "target": { "key": "57209de11350f99a54387ea1cad779c00153a98d40a145c946a69f9800148d80" } } ], "extra": [ 1, 53, 62, 232, 172, 218, 113, 69, 180, 232, 123, 33, 188, 217, 8, 213, 227, 126, 94, 163, 210, 223, 186, 21, 195, 90, 44, 168, 252, 25, 82, 32, 183, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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