Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7483ead45bf38a9b902c07ce13e8f991b0a2fb8ff2ab5c2c8b12551f68ebd480

Tx prefix hash: 1b7a17feab6bcf53059df65c2b9a9ca9085634b4a746b7c0f64b669957494e9c
Tx public key: 66d1e8138a1b44cb682736092b4cf038fd3da9d221fa1098636cd0eec1a5d1d2
Timestamp: 1702344829 Timestamp [UCT]: 2023-12-12 01:33:49 Age [y:d:h:m:s]: 01:030:10:22:11
Block: 911184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283112 RingCT/type: yes/0
Extra: 0166d1e8138a1b44cb682736092b4cf038fd3da9d221fa1098636cd0eec1a5d1d202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36054923de284bedabcbf39f8a56ecd11ddd472f58f82c41d6d7ff52a043c429 0.600000000000 1368365 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": 911194, "vin": [ { "gen": { "height": 911184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36054923de284bedabcbf39f8a56ecd11ddd472f58f82c41d6d7ff52a043c429" } } ], "extra": [ 1, 102, 209, 232, 19, 138, 27, 68, 203, 104, 39, 54, 9, 43, 76, 240, 56, 253, 61, 169, 210, 33, 250, 16, 152, 99, 108, 208, 238, 193, 165, 209, 210, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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