Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0feb409769e9b676e715f1a91ffbbba4c22e99c31bd97be6b1b3b6e8966df85a

Tx prefix hash: 4a9418c896f53eb1bc1df0ed701416cf91e1fc973228a29fb191d93f69de1b10
Tx public key: 4ff1fbddac823804077a27398bad2146647014ad9a8354b53baca8f92f8a3bf9
Timestamp: 1579189654 Timestamp [UCT]: 2020-01-16 15:47:34 Age [y:d:h:m:s]: 04:348:00:42:04
Block: 46919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138208 RingCT/type: yes/0
Extra: 014ff1fbddac823804077a27398bad2146647014ad9a8354b53baca8f92f8a3bf902110000003adcee4b4d000000000000000000

1 output(s) for total of 429.080436241000 dcy

stealth address amount amount idx
00: e7a541464afee70bd56fbc10eedbe6ab34d7ef914cc75ad811a6cd67329b6228 429.080436241000 86543 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": 46929, "vin": [ { "gen": { "height": 46919 } } ], "vout": [ { "amount": 429080436241, "target": { "key": "e7a541464afee70bd56fbc10eedbe6ab34d7ef914cc75ad811a6cd67329b6228" } } ], "extra": [ 1, 79, 241, 251, 221, 172, 130, 56, 4, 7, 122, 39, 57, 139, 173, 33, 70, 100, 112, 20, 173, 154, 131, 84, 181, 59, 172, 168, 249, 47, 138, 59, 249, 2, 17, 0, 0, 0, 58, 220, 238, 75, 77, 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