Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 930558d29b2a69237cd7aaa1e0dc7ca000cbbb57eb1bb5b538af015be202d1a4

Tx prefix hash: f42b3927fd3e5239bebb848fc737fcb18d94388af502e334f3c640cfb7dd3f70
Tx public key: 6ecbd24255fe0f4be8c8b4198884fac3dfb1825f2f6f773fc6128671cb093ee9
Timestamp: 1717245295 Timestamp [UCT]: 2024-06-01 12:34:55 Age [y:d:h:m:s]: 00:303:01:05:45
Block: 1034728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216569 RingCT/type: yes/0
Extra: 016ecbd24255fe0f4be8c8b4198884fac3dfb1825f2f6f773fc6128671cb093ee902110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46f45e2514724bcf0a2c8080a9fd36649c1552599eb13e0cd900e5946d81774e 0.600000000000 1503247 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": 1034738, "vin": [ { "gen": { "height": 1034728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46f45e2514724bcf0a2c8080a9fd36649c1552599eb13e0cd900e5946d81774e" } } ], "extra": [ 1, 110, 203, 210, 66, 85, 254, 15, 75, 232, 200, 180, 25, 136, 132, 250, 195, 223, 177, 130, 95, 47, 111, 119, 63, 198, 18, 134, 113, 203, 9, 62, 233, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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