Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 034bc154dafd6beb50ed5f71f50ae5e1ecf26fc9244093ccedef88487c6431d3

Tx prefix hash: 8410d23dd892e8afe3c132c42e72535d1d821da60a8f64460c4ba9fbbcf6ddb1
Tx public key: 8300a991ccdae33b99ea4fa6be4103d6eac12a068d35600dd4afc53d08fa4f11
Timestamp: 1719309981 Timestamp [UCT]: 2024-06-25 10:06:21 Age [y:d:h:m:s]: 00:276:06:58:00
Block: 1051827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197426 RingCT/type: yes/0
Extra: 018300a991ccdae33b99ea4fa6be4103d6eac12a068d35600dd4afc53d08fa4f1102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b773589f7d4a539a68a09a84cc8a2967ec510a2d8a0aaafab4ce435a68dddbc5 0.600000000000 1522146 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": 1051837, "vin": [ { "gen": { "height": 1051827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b773589f7d4a539a68a09a84cc8a2967ec510a2d8a0aaafab4ce435a68dddbc5" } } ], "extra": [ 1, 131, 0, 169, 145, 204, 218, 227, 59, 153, 234, 79, 166, 190, 65, 3, 214, 234, 193, 42, 6, 141, 53, 96, 13, 212, 175, 197, 61, 8, 250, 79, 17, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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