Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0254b649845593446626842c381e33f2497c7a375a93e84aeba80b284eaed38f

Tx prefix hash: b3b6d784f6c8b653f3a9d930939c9ad1459e2f5c657754c08b1bcad8ee50afcf
Tx public key: 855fef9a3b682c94307badb1b5012a184f105377f5e986c8b7213d179d7fb663
Timestamp: 1729479598 Timestamp [UCT]: 2024-10-21 02:59:58 Age [y:d:h:m:s]: 00:164:12:08:50
Block: 1136104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117382 RingCT/type: yes/0
Extra: 01855fef9a3b682c94307badb1b5012a184f105377f5e986c8b7213d179d7fb663021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1490c46398b8a0d7d609814742fdad0fcfebd42b33b82ac7d3ed4a809f643336 0.600000000000 1619447 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": 1136114, "vin": [ { "gen": { "height": 1136104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1490c46398b8a0d7d609814742fdad0fcfebd42b33b82ac7d3ed4a809f643336" } } ], "extra": [ 1, 133, 95, 239, 154, 59, 104, 44, 148, 48, 123, 173, 177, 181, 1, 42, 24, 79, 16, 83, 119, 245, 233, 134, 200, 183, 33, 61, 23, 157, 127, 182, 99, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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