Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db9fe2f79485b44a82e72fcbfab42c54f5074028bf52376c48bf3ab0b1045f95

Tx prefix hash: 955be02655a946b7b9bac3781ffa7360b1d5e7db4ea742e30003919ae02b6b80
Tx public key: 5c1ef70f5068382f3fb6e8ceba4c576e2a1c0cd2f7b8eec8b8706462d6290ba2
Timestamp: 1671525235 Timestamp [UCT]: 2022-12-20 08:33:55 Age [y:d:h:m:s]: 02:108:16:35:44
Block: 656555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 599366 RingCT/type: yes/0
Extra: 015c1ef70f5068382f3fb6e8ceba4c576e2a1c0cd2f7b8eec8b8706462d6290ba2021100000002e6d27f9c000000000000000000

1 output(s) for total of 4.097893931000 dcy

stealth address amount amount idx
00: 1318f418cfe2b394d6dc47ef4c9a2aaace4837a5b67f03bfb1da3b1d0a9a5886 4.097893931000 1097164 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": 656565, "vin": [ { "gen": { "height": 656555 } } ], "vout": [ { "amount": 4097893931, "target": { "key": "1318f418cfe2b394d6dc47ef4c9a2aaace4837a5b67f03bfb1da3b1d0a9a5886" } } ], "extra": [ 1, 92, 30, 247, 15, 80, 104, 56, 47, 63, 182, 232, 206, 186, 76, 87, 110, 42, 28, 12, 210, 247, 184, 238, 200, 184, 112, 100, 98, 214, 41, 11, 162, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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