Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 056bd6602ce249a4f027710967dfe7aa32cc274833eff6112654d07caad686c1

Tx prefix hash: 076640279e6407f7ad87872595674a841488de20fd341e386ac5c5d1b4c43856
Tx public key: 9f58a20f3dc3fd7ff13093c2ae2cc29b8d3d61e4ced79dad1d67dfc6012c91b8
Timestamp: 1710807608 Timestamp [UCT]: 2024-03-19 00:20:08 Age [y:d:h:m:s]: 01:015:18:49:11
Block: 981363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272235 RingCT/type: yes/0
Extra: 019f58a20f3dc3fd7ff13093c2ae2cc29b8d3d61e4ced79dad1d67dfc6012c91b8021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cb6cca286954c34e5ac742c1fdcfbf77896d3a1e66fa5b374ec5760d023eea4 0.600000000000 1441458 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": 981373, "vin": [ { "gen": { "height": 981363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cb6cca286954c34e5ac742c1fdcfbf77896d3a1e66fa5b374ec5760d023eea4" } } ], "extra": [ 1, 159, 88, 162, 15, 61, 195, 253, 127, 241, 48, 147, 194, 174, 44, 194, 155, 141, 61, 97, 228, 206, 215, 157, 173, 29, 103, 223, 198, 1, 44, 145, 184, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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