Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3277f0d74985196c892d3e5bee9a032c5967255314ec099e0e64d809c0910ea2

Tx prefix hash: 598d30f9f8b4164946fa4e7528b13fbd30da3e1fc6d93a96b258ca12139e2468
Tx public key: 6d19087b345221573f7523066ab4fafa6b476b5a04b0bcd044fc5154957b6f0e
Timestamp: 1645597965 Timestamp [UTC]: 2022-02-23 06:32:45 Age [y:d:h:m:s]: 04:007:02:26:50
Block: 444592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1043647 RingCT/type: yes/0
Extra: 016d19087b345221573f7523066ab4fafa6b476b5a04b0bcd044fc5154957b6f0e0211000000024a0f5013000000000000000000

1 output(s) for total of 0.020648211107 xmr

stealth address amount amount idx tag
00: c7e1a493ddec906f874ab296dc5f1c9dcaffaab912a2081d3797c5b6a66acf87 0.020648211107 857923 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 dinastycoin-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": 444602, "vin": [ { "gen": { "height": 444592 } } ], "vout": [ { "amount": 20648211107, "target": { "key": "c7e1a493ddec906f874ab296dc5f1c9dcaffaab912a2081d3797c5b6a66acf87" } } ], "extra": [ 1, 109, 25, 8, 123, 52, 82, 33, 87, 63, 117, 35, 6, 106, 180, 250, 250, 107, 71, 107, 90, 4, 176, 188, 208, 68, 252, 81, 84, 149, 123, 111, 14, 2, 17, 0, 0, 0, 2, 74, 15, 80, 19, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369