Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 400d90748647d1b6e4e8123d2217f3ec4c0f7073c69349b63894643aa7ff31d9

Tx prefix hash: 928b5dbb09ec0df8be9236c9d725c5ccec27ee05aa99c5a6f145b55d5b86d412
Tx public key: 4a064097556bf7dfa973979a779c8ad4ea9050af409ba31d4814846cedd4418a
Timestamp: 1577775275 Timestamp [UCT]: 2019-12-31 06:54:35 Age [y:d:h:m:s]: 05:132:16:20:54
Block: 35524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244665 RingCT/type: yes/0
Extra: 014a064097556bf7dfa973979a779c8ad4ea9050af409ba31d4814846cedd4418a02110000001b4ac5aa02000000000000000000

1 output(s) for total of 468.063207106000 dcy

stealth address amount amount idx
00: 573a9d781eeed81ff89b854f288cc5dd1c75212dfef94ce469a3580392eb8540 468.063207106000 59950 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": 35534, "vin": [ { "gen": { "height": 35524 } } ], "vout": [ { "amount": 468063207106, "target": { "key": "573a9d781eeed81ff89b854f288cc5dd1c75212dfef94ce469a3580392eb8540" } } ], "extra": [ 1, 74, 6, 64, 151, 85, 107, 247, 223, 169, 115, 151, 154, 119, 156, 138, 212, 234, 144, 80, 175, 64, 155, 163, 29, 72, 20, 132, 108, 237, 212, 65, 138, 2, 17, 0, 0, 0, 27, 74, 197, 170, 2, 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