Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 551cb8be01c0347410bf3cec9caeb8a2f5467ce8b9ec02b55bd56dcbca076bc5

Tx prefix hash: 515939bbba2ea3b1fc7c03c62afdc3a4cf0c6da14ce5849d1085b862781d83f8
Tx public key: c46c901faf69cf33bd1b829b55a25e391e8f3cf143cc5ab07b641142f4dd6528
Timestamp: 1723330218 Timestamp [UCT]: 2024-08-10 22:50:18 Age [y:d:h:m:s]: 01:090:11:54:08
Block: 1085163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323153 RingCT/type: yes/0
Extra: 01c46c901faf69cf33bd1b829b55a25e391e8f3cf143cc5ab07b641142f4dd6528021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4448b1aad2ad66bb9b855f9573a9142972ca5961d8f52aa6ba3b945968fa014 0.600000000000 1559688 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": 1085173, "vin": [ { "gen": { "height": 1085163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4448b1aad2ad66bb9b855f9573a9142972ca5961d8f52aa6ba3b945968fa014" } } ], "extra": [ 1, 196, 108, 144, 31, 175, 105, 207, 51, 189, 27, 130, 155, 85, 162, 94, 57, 30, 143, 60, 241, 67, 204, 90, 176, 123, 100, 17, 66, 244, 221, 101, 40, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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