Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b25261ca50fbe28839b4d41acf1e062bf89fa3139cd5b4c22bfaeafe033a641

Tx prefix hash: fc8847d00a77a9ac2de0e6db35bc9365dbb8ff6c9944f311f138cbd9ebd74fc2
Tx public key: fa4a191fbd7e2cb1f7b2461b7fad5fabad1b075818510646cf7fe8b90da4875d
Timestamp: 1702769724 Timestamp [UCT]: 2023-12-16 23:35:24 Age [y:d:h:m:s]: 01:027:01:28:16
Block: 914707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280690 RingCT/type: yes/0
Extra: 01fa4a191fbd7e2cb1f7b2461b7fad5fabad1b075818510646cf7fe8b90da4875d021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e0eac2c3463d29a3f9eac4010f3ece5896f5f17a2b619e7ecb7f3ab95957b4c 0.600000000000 1372059 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": 914717, "vin": [ { "gen": { "height": 914707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e0eac2c3463d29a3f9eac4010f3ece5896f5f17a2b619e7ecb7f3ab95957b4c" } } ], "extra": [ 1, 250, 74, 25, 31, 189, 126, 44, 177, 247, 178, 70, 27, 127, 173, 95, 171, 173, 27, 7, 88, 24, 81, 6, 70, 207, 127, 232, 185, 13, 164, 135, 93, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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