Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559dddb9d1f47eae107d798c29ef5e950f1c79208ef72224e44ceba62f69ff52

Tx prefix hash: 9299490b9480c89401b126e7e2bdbbb1419f18f8814e0ae2d4da23b12f93a71d
Tx public key: b2e95a81efee4c3936cf8ee85295d0bd63a3114dbda68a1165bffd8bc1da5749
Timestamp: 1710118664 Timestamp [UCT]: 2024-03-11 00:57:44 Age [y:d:h:m:s]: 01:270:05:51:46
Block: 975644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451879 RingCT/type: yes/0
Extra: 01b2e95a81efee4c3936cf8ee85295d0bd63a3114dbda68a1165bffd8bc1da57490211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7262f736f5b2876fdba0b8fe075f67d33c0659e6435e2b6dfd2cc5bfd2930532 0.600000000000 1435617 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": 975654, "vin": [ { "gen": { "height": 975644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7262f736f5b2876fdba0b8fe075f67d33c0659e6435e2b6dfd2cc5bfd2930532" } } ], "extra": [ 1, 178, 233, 90, 129, 239, 238, 76, 57, 54, 207, 142, 232, 82, 149, 208, 189, 99, 163, 17, 77, 189, 166, 138, 17, 101, 191, 253, 139, 193, 218, 87, 73, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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