Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fb4a8183cc8cd059b0d319b7c8050c074e3074f98ffc63ca790aeedfed4db8a

Tx prefix hash: 4d7d1b3632f0d91766ec49e8578fed01b5d50bbc9131e91300e6dbefd4301e55
Tx public key: 057dcaf6b87040ed07a595e60487bb95fe25947ae862fc70ac8e8d27f2edcdb7
Timestamp: 1700368764 Timestamp [UCT]: 2023-11-19 04:39:24 Age [y:d:h:m:s]: 01:355:20:42:27
Block: 894802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513222 RingCT/type: yes/0
Extra: 01057dcaf6b87040ed07a595e60487bb95fe25947ae862fc70ac8e8d27f2edcdb7021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.665502230000 dcy

stealth address amount amount idx
00: 9372d74079456bd95b423f2ded186740e83e2fcd9bac1d3dceaffbcade894865 0.665502230000 1351013 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": 894812, "vin": [ { "gen": { "height": 894802 } } ], "vout": [ { "amount": 665502230, "target": { "key": "9372d74079456bd95b423f2ded186740e83e2fcd9bac1d3dceaffbcade894865" } } ], "extra": [ 1, 5, 125, 202, 246, 184, 112, 64, 237, 7, 165, 149, 230, 4, 135, 187, 149, 254, 37, 148, 122, 232, 98, 252, 112, 172, 142, 141, 39, 242, 237, 205, 183, 2, 17, 0, 0, 0, 3, 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