Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 715effa480e8e4d508c930f5eeedd390e7434ce4bf05657e28db774a0b1a6e29

Tx prefix hash: 6ff669879397e0ba69d42b5a50e9d6f135286c96d941a6e915386aea9f0d9925
Tx public key: e53c72349e96c375779cd07a1ee0f53d20fa51f113f76de4f9e79e09d47e4ea0
Timestamp: 1722487243 Timestamp [UCT]: 2024-08-01 04:40:43 Age [y:d:h:m:s]: 00:300:17:21:46
Block: 1078166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214876 RingCT/type: yes/0
Extra: 01e53c72349e96c375779cd07a1ee0f53d20fa51f113f76de4f9e79e09d47e4ea0021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70a01315c52151839ed8e9425bfcdb3e260d62f327c1ffd88fd20556270be793 0.600000000000 1550733 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": 1078176, "vin": [ { "gen": { "height": 1078166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70a01315c52151839ed8e9425bfcdb3e260d62f327c1ffd88fd20556270be793" } } ], "extra": [ 1, 229, 60, 114, 52, 158, 150, 195, 117, 119, 156, 208, 122, 30, 224, 245, 61, 32, 250, 81, 241, 19, 247, 109, 228, 249, 231, 158, 9, 212, 126, 78, 160, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 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