Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81f083940b25ef6b06d1fd9d1c30182c1f217911d31a96991f004f9eb645595d

Tx prefix hash: 807118b09da4a6750bfd3771be0734452683f35c075fc2c1facd1cae3ef2f4ce
Tx public key: 0d9847fc11284f129bb40c3270fd042f8c074e1f7ae47ae29a79b06ea34c52d0
Timestamp: 1720167607 Timestamp [UCT]: 2024-07-05 08:20:07 Age [y:d:h:m:s]: 00:252:15:13:06
Block: 1058936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180514 RingCT/type: yes/0
Extra: 010d9847fc11284f129bb40c3270fd042f8c074e1f7ae47ae29a79b06ea34c52d00211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d63a5fda024ef9ca7924f825c7f5c94c89023c25ca01497970b7150985e17401 0.600000000000 1529395 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": 1058946, "vin": [ { "gen": { "height": 1058936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d63a5fda024ef9ca7924f825c7f5c94c89023c25ca01497970b7150985e17401" } } ], "extra": [ 1, 13, 152, 71, 252, 17, 40, 79, 18, 155, 180, 12, 50, 112, 253, 4, 47, 140, 7, 78, 31, 122, 228, 122, 226, 154, 121, 176, 110, 163, 76, 82, 208, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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