Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 966a4c80c94aa20a9c29d98621d918b14691856dbdd787a1db0ed27746513570

Tx prefix hash: 8923a0f3631964a8112a46d96d1dab5d989c62a806189ff9e2dcf1a5df3d67c4
Tx public key: 6bd25fb6afb293c4888cd48e8e5fe85443f4dacb7ea4541f8f74873c1d62b5d5
Timestamp: 1689527634 Timestamp [UCT]: 2023-07-16 17:13:54 Age [y:d:h:m:s]: 01:181:09:26:23
Block: 805191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390969 RingCT/type: yes/0
Extra: 016bd25fb6afb293c4888cd48e8e5fe85443f4dacb7ea4541f8f74873c1d62b5d502110000000375e3f0e9000000000000000000

1 output(s) for total of 1.318463431000 dcy

stealth address amount amount idx
00: dd90637954b44eab582ae18a433ca31d3edc90be868bcfe6ea0a6b51e411bb10 1.318463431000 1256412 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": 805201, "vin": [ { "gen": { "height": 805191 } } ], "vout": [ { "amount": 1318463431, "target": { "key": "dd90637954b44eab582ae18a433ca31d3edc90be868bcfe6ea0a6b51e411bb10" } } ], "extra": [ 1, 107, 210, 95, 182, 175, 178, 147, 196, 136, 140, 212, 142, 142, 95, 232, 84, 67, 244, 218, 203, 126, 164, 84, 31, 143, 116, 135, 60, 29, 98, 181, 213, 2, 17, 0, 0, 0, 3, 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