Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f15e52e5baed98fbbc5d4b64d643aee10a9b4be049dc467e878f20c95458eef6

Tx prefix hash: a23608c5f6ae19532c73ae076760b59092cee2cfc8b91375a6ec9a29708c5ae5
Tx public key: 23f04983d50b3c55c9fc3122ee39a22b2cbeeb2d8848178b42591726fe60eb0e
Timestamp: 1705777410 Timestamp [UCT]: 2024-01-20 19:03:30 Age [y:d:h:m:s]: 01:351:01:47:58
Block: 939614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509829 RingCT/type: yes/0
Extra: 0123f04983d50b3c55c9fc3122ee39a22b2cbeeb2d8848178b42591726fe60eb0e0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 899c5ed043e8399808d8fcaf19d2ee233cfd43dff3211fb47176793d48d62b67 0.600000000000 1397724 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": 939624, "vin": [ { "gen": { "height": 939614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "899c5ed043e8399808d8fcaf19d2ee233cfd43dff3211fb47176793d48d62b67" } } ], "extra": [ 1, 35, 240, 73, 131, 213, 11, 60, 85, 201, 252, 49, 34, 238, 57, 162, 43, 44, 190, 235, 45, 136, 72, 23, 139, 66, 89, 23, 38, 254, 96, 235, 14, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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