Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8f10120d21f50b623f9e859d393f3139a609fab303f23bfc31a5ecd4e21f7fa

Tx prefix hash: 604593df016b7066bd5f125d6d54d90ab55d075380251aa490eaf1dbf8122810
Tx public key: d29147ce09c900430b5c72ff944477e9e093d9c62f44f9390ad23e1ca2ed8c8c
Timestamp: 1720672943 Timestamp [UCT]: 2024-07-11 04:42:23 Age [y:d:h:m:s]: 01:118:21:31:06
Block: 1063143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343475 RingCT/type: yes/0
Extra: 01d29147ce09c900430b5c72ff944477e9e093d9c62f44f9390ad23e1ca2ed8c8c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46af745e84e4649e6748f26127d1c60b7ef3c9989bee1d52b770ea05d7abb23c 0.600000000000 1533658 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": 1063153, "vin": [ { "gen": { "height": 1063143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46af745e84e4649e6748f26127d1c60b7ef3c9989bee1d52b770ea05d7abb23c" } } ], "extra": [ 1, 210, 145, 71, 206, 9, 201, 0, 67, 11, 92, 114, 255, 148, 68, 119, 233, 224, 147, 217, 198, 47, 68, 249, 57, 10, 210, 62, 28, 162, 237, 140, 140, 2, 17, 0, 0, 0, 1, 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