Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f90a0ecaef2df2155da14869b3e1d8fe5742bb7a0e6fbb0600651fbd2124a75

Tx prefix hash: a002806f03f2f66a5c5284971d4338620e8f892c82ed94ffcb04633340202dab
Tx public key: d64dd29c0aad9b80244c3438fa5c6c2f94c3cac3035113d911778e402ea3edb2
Timestamp: 1710365725 Timestamp [UCT]: 2024-03-13 21:35:25 Age [y:d:h:m:s]: 01:251:14:28:21
Block: 977696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438523 RingCT/type: yes/0
Extra: 01d64dd29c0aad9b80244c3438fa5c6c2f94c3cac3035113d911778e402ea3edb202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5a642cf81a6677c2213e760a81b9ada50a1436b0b1ffdc1a34ce271c006abb6 0.600000000000 1437699 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": 977706, "vin": [ { "gen": { "height": 977696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5a642cf81a6677c2213e760a81b9ada50a1436b0b1ffdc1a34ce271c006abb6" } } ], "extra": [ 1, 214, 77, 210, 156, 10, 173, 155, 128, 36, 76, 52, 56, 250, 92, 108, 47, 148, 195, 202, 195, 3, 81, 19, 217, 17, 119, 142, 64, 46, 163, 237, 178, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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