Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c5fbc8b032f8dc134cd32a96fa100d6f8a6f01706f9cfd81dabe7002d968fdc

Tx prefix hash: 0b7f6089bc2d01735886a3739ed193586c2f4559bd5eb4f4b18afd315de8ce7c
Tx public key: 2a027eae40f4247b90442589faae459daa0b06399649e27e544731296369c4ce
Timestamp: 1673435296 Timestamp [UCT]: 2023-01-11 11:08:16 Age [y:d:h:m:s]: 02:103:05:17:14
Block: 672371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 595455 RingCT/type: yes/0
Extra: 012a027eae40f4247b90442589faae459daa0b06399649e27e544731296369c4ce0211000000038b7b6602000000000000000000

1 output(s) for total of 3.632082597000 dcy

stealth address amount amount idx
00: 7ae448189552d46b2ab2d92c8848b02db5aac9b7238f853d730995c9c4f53865 3.632082597000 1113906 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 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": 672381, "vin": [ { "gen": { "height": 672371 } } ], "vout": [ { "amount": 3632082597, "target": { "key": "7ae448189552d46b2ab2d92c8848b02db5aac9b7238f853d730995c9c4f53865" } } ], "extra": [ 1, 42, 2, 126, 174, 64, 244, 36, 123, 144, 68, 37, 137, 250, 174, 69, 157, 170, 11, 6, 57, 150, 73, 226, 126, 84, 71, 49, 41, 99, 105, 196, 206, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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