Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1e09127a513711baa02c64e44081f70344a3a792a1e4e49b53df11aab04ac7b

Tx prefix hash: 8307086c9ec535819b5b021755a5b4341ee44e615e2784cd7da50d5e20ffcf30
Tx public key: 17e3ae3a686ac4e52a0e8cdb4f77eeacef20d6bd9bc20c70a235ad542fe2f62f
Timestamp: 1726922116 Timestamp [UCT]: 2024-09-21 12:35:16 Age [y:d:h:m:s]: 00:207:05:40:04
Block: 1114951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147923 RingCT/type: yes/0
Extra: 0117e3ae3a686ac4e52a0e8cdb4f77eeacef20d6bd9bc20c70a235ad542fe2f62f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82918aef4fc544db699a8f344163497b100b1ba49e0db81bf0575d4f0b2a6774 0.600000000000 1594906 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": 1114961, "vin": [ { "gen": { "height": 1114951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82918aef4fc544db699a8f344163497b100b1ba49e0db81bf0575d4f0b2a6774" } } ], "extra": [ 1, 23, 227, 174, 58, 104, 106, 196, 229, 42, 14, 140, 219, 79, 119, 238, 172, 239, 32, 214, 189, 155, 194, 12, 112, 162, 53, 173, 84, 47, 226, 246, 47, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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