Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5fcd0a4aa659655d0890d0c5cba133b8d7989065ad372f76610d839a16456c0

Tx prefix hash: 4cfe06c75aaf6bd8097f423deb9235b2cbf363326bc0cd4b8b57c6b65bb82a93
Tx public key: f8ad574519d48fbea97faa1d2b837e58f7bb7b1de587f98f7586a20313b3f605
Timestamp: 1706730009 Timestamp [UCT]: 2024-01-31 19:40:09 Age [y:d:h:m:s]: 01:082:19:47:03
Block: 947517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320287 RingCT/type: yes/0
Extra: 01f8ad574519d48fbea97faa1d2b837e58f7bb7b1de587f98f7586a20313b3f60502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35c356d84f5a791a229a0f2c8ba2365f6c7893b549c02f753ecad425c03792e1 0.600000000000 1405869 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": 947527, "vin": [ { "gen": { "height": 947517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35c356d84f5a791a229a0f2c8ba2365f6c7893b549c02f753ecad425c03792e1" } } ], "extra": [ 1, 248, 173, 87, 69, 25, 212, 143, 190, 169, 127, 170, 29, 43, 131, 126, 88, 247, 187, 123, 29, 229, 135, 249, 143, 117, 134, 162, 3, 19, 179, 246, 5, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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