Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a88806490998761369d391924ef96e0aebb4f6eadde5735924d79c70d0776544

Tx prefix hash: 1796933ef36f4f628e0daf9783097a413dff3f376a5b9e86afc115262fd389db
Tx public key: 8f3da12f69787fd67f4712c2c3b037a1b7993ecd1df7fc9e19161acbaf4c2cee
Timestamp: 1723044509 Timestamp [UCT]: 2024-08-07 15:28:29 Age [y:d:h:m:s]: 00:254:02:16:58
Block: 1082792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181508 RingCT/type: yes/0
Extra: 018f3da12f69787fd67f4712c2c3b037a1b7993ecd1df7fc9e19161acbaf4c2cee02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8cf32520ee721838cfb9f990808623ccedfcddbaba4c58d42595b8ecd16d956 0.600000000000 1556623 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": 1082802, "vin": [ { "gen": { "height": 1082792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8cf32520ee721838cfb9f990808623ccedfcddbaba4c58d42595b8ecd16d956" } } ], "extra": [ 1, 143, 61, 161, 47, 105, 120, 127, 214, 127, 71, 18, 194, 195, 176, 55, 161, 183, 153, 62, 205, 29, 247, 252, 158, 25, 22, 26, 203, 175, 76, 44, 238, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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