Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45263baee61d3977d16c67397ccbf3f28dcdf3a77e8cd580ff5dffe190809d51

Tx prefix hash: b57f47e4f5cfe068a32b842d24f6e80452cb194102696b7ccada251bb781385e
Tx public key: 3481846d95e302a6b7c5e6c5ecd08c7480c8dccb3543ff8fe8c80060753ecaf8
Timestamp: 1577795505 Timestamp [UCT]: 2019-12-31 12:31:45 Age [y:d:h:m:s]: 05:052:10:08:49
Block: 35723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1187214 RingCT/type: yes/0
Extra: 013481846d95e302a6b7c5e6c5ecd08c7480c8dccb3543ff8fe8c80060753ecaf80211000000038a2ee0d9000000000000000000

1 output(s) for total of 467.351032236000 dcy

stealth address amount amount idx
00: 055fb8dca5a814e601194b4c606393277b32308454f460fb831d097b2c128d3d 467.351032236000 60326 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": 35733, "vin": [ { "gen": { "height": 35723 } } ], "vout": [ { "amount": 467351032236, "target": { "key": "055fb8dca5a814e601194b4c606393277b32308454f460fb831d097b2c128d3d" } } ], "extra": [ 1, 52, 129, 132, 109, 149, 227, 2, 166, 183, 197, 230, 197, 236, 208, 140, 116, 128, 200, 220, 203, 53, 67, 255, 143, 232, 200, 0, 96, 117, 62, 202, 248, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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