Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b01169a4dc5af3b821d4935f777852951dbf5f2d8f6cc2f71d3a4d1f7ee6794

Tx prefix hash: d9f71ae5ce538dfa3eebb6345e510f57b2a84a44b5bae73d26285a4ccb31690e
Tx public key: 7ecdbb10734aab7418fbf598d98df18135202595f234caa19145e85b7ee1339b
Timestamp: 1635941725 Timestamp [UCT]: 2021-11-03 12:15:25 Age [y:d:h:m:s]: 03:131:02:00:18
Block: 366461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 871996 RingCT/type: yes/0
Extra: 017ecdbb10734aab7418fbf598d98df18135202595f234caa19145e85b7ee1339b021100000002f56b629f000000000000000000

1 output(s) for total of 37.476841440000 dcy

stealth address amount amount idx
00: d711bb3b7d01b8e6cc974ad3f4595ea214636239cefe4279459110fd8a0a19b4 37.476841440000 743881 of 0

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": 366471, "vin": [ { "gen": { "height": 366461 } } ], "vout": [ { "amount": 37476841440, "target": { "key": "d711bb3b7d01b8e6cc974ad3f4595ea214636239cefe4279459110fd8a0a19b4" } } ], "extra": [ 1, 126, 205, 187, 16, 115, 74, 171, 116, 24, 251, 245, 152, 217, 141, 241, 129, 53, 32, 37, 149, 242, 52, 202, 161, 145, 69, 232, 91, 126, 225, 51, 155, 2, 17, 0, 0, 0, 2, 245, 107, 98, 159, 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