Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f606bb4e604af50148e4d28cf8b1a593f266add21151ef52bf28253a59153f6e

Tx prefix hash: 3e8c0abf12bd26fd08f7d403c069598daa8fb010339044e51adcfedb614c9f67
Tx public key: 579245ea600f7257335d1b671af0e6791fdbde93cb904c794c92bb822faae55e
Timestamp: 1694794785 Timestamp [UCT]: 2023-09-15 16:19:45 Age [y:d:h:m:s]: 01:180:23:16:05
Block: 848778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390436 RingCT/type: yes/0
Extra: 01579245ea600f7257335d1b671af0e6791fdbde93cb904c794c92bb822faae55e02110000000ce6d27f9c000000000000000000

1 output(s) for total of 0.945466619000 dcy

stealth address amount amount idx
00: 20fba4d055f9ff0e431ba6c39af985c3aa8ea2f7b307a3ac3205acf603217666 0.945466619000 1302404 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": 848788, "vin": [ { "gen": { "height": 848778 } } ], "vout": [ { "amount": 945466619, "target": { "key": "20fba4d055f9ff0e431ba6c39af985c3aa8ea2f7b307a3ac3205acf603217666" } } ], "extra": [ 1, 87, 146, 69, 234, 96, 15, 114, 87, 51, 93, 27, 103, 26, 240, 230, 121, 31, 219, 222, 147, 203, 144, 76, 121, 76, 146, 187, 130, 47, 170, 229, 94, 2, 17, 0, 0, 0, 12, 230, 210, 127, 156, 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