Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b76293e0d948df65e23297693c95ea4796961525b98eeda50deec2daabdb7a6

Tx prefix hash: 466b58a5adcb39f0b8adb2806a563cb86a0759c88071a3f6559923a631b76a59
Tx public key: 0201003c5af5b5cd995530fd580f20a1c253603a2eddcf3c938b01402377d3ba
Timestamp: 1705186467 Timestamp [UCT]: 2024-01-13 22:54:27 Age [y:d:h:m:s]: 01:064:07:43:56
Block: 934731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307064 RingCT/type: yes/0
Extra: 010201003c5af5b5cd995530fd580f20a1c253603a2eddcf3c938b01402377d3ba02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e038272329452ce507d7e4a002bb247a94fff03efcf96d49a94299b40f892c6 0.600000000000 1392747 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": 934741, "vin": [ { "gen": { "height": 934731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e038272329452ce507d7e4a002bb247a94fff03efcf96d49a94299b40f892c6" } } ], "extra": [ 1, 2, 1, 0, 60, 90, 245, 181, 205, 153, 85, 48, 253, 88, 15, 32, 161, 194, 83, 96, 58, 46, 221, 207, 60, 147, 139, 1, 64, 35, 119, 211, 186, 2, 17, 0, 0, 0, 5, 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