Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec725d2ad2665100462ecdeea4ac44a950eaa3ffaf4a426d7e198e3b6f98fbf7

Tx prefix hash: cc3dfd7a8c1e8c33eebcef9dc82b5e507149dc23147bfc6bbe11695be6c69fda
Tx public key: c76d0b4d8090d64fa5114f4c87d3144f4e5b7a56ea52411ceb6a0b86e6530d26
Timestamp: 1727387187 Timestamp [UCT]: 2024-09-26 21:46:27 Age [y:d:h:m:s]: 00:212:15:09:18
Block: 1118802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151794 RingCT/type: yes/0
Extra: 01c76d0b4d8090d64fa5114f4c87d3144f4e5b7a56ea52411ceb6a0b86e6530d26021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4381f9ce09e1d28c232b023d77a338e2c932f306445f178973de1025d933a5d9 0.600000000000 1600123 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": 1118812, "vin": [ { "gen": { "height": 1118802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4381f9ce09e1d28c232b023d77a338e2c932f306445f178973de1025d933a5d9" } } ], "extra": [ 1, 199, 109, 11, 77, 128, 144, 214, 79, 165, 17, 79, 76, 135, 211, 20, 79, 78, 91, 122, 86, 234, 82, 65, 28, 235, 106, 11, 134, 230, 83, 13, 38, 2, 17, 0, 0, 0, 3, 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