Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd71b1e1f7c054fb4d29accc4296ee52bff7d1c63ac0eada1f85e18f6b152f8e

Tx prefix hash: c43185f7ef86b32742f2bafc55cbf59ea43ae27e9122bccbd53674165f2c2615
Tx public key: 17347a25c9204e90e11a002d0fd0b1fd428f770fe5cefe421e95f2314fac37ee
Timestamp: 1713905342 Timestamp [UCT]: 2024-04-23 20:49:02 Age [y:d:h:m:s]: 00:348:10:53:03
Block: 1007028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249094 RingCT/type: yes/0
Extra: 0117347a25c9204e90e11a002d0fd0b1fd428f770fe5cefe421e95f2314fac37ee0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e86cf4b64e71a0f584ef1df27cd8589f9facd1986b76ac220c1a5bdfe44a2de 0.600000000000 1468242 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": 1007038, "vin": [ { "gen": { "height": 1007028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e86cf4b64e71a0f584ef1df27cd8589f9facd1986b76ac220c1a5bdfe44a2de" } } ], "extra": [ 1, 23, 52, 122, 37, 201, 32, 78, 144, 225, 26, 0, 45, 15, 208, 177, 253, 66, 143, 119, 15, 229, 206, 254, 66, 30, 149, 242, 49, 79, 172, 55, 238, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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