Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 303e3b04ac08bb48be8e23239798299c4fd746ce235d9223f75f12526cbb1e6f

Tx prefix hash: ecb4b54b5ea3a5f0695ed03c49a4a2d4b0fe6587aeec1491d659f5b6658a4a83
Tx public key: 7d78d76b97e43aa2b777ce3094d054525982eb45d0b7ad95391ebfc1683b8bb0
Timestamp: 1721806016 Timestamp [UCT]: 2024-07-24 07:26:56 Age [y:d:h:m:s]: 00:250:12:29:00
Block: 1072520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178965 RingCT/type: yes/0
Extra: 017d78d76b97e43aa2b777ce3094d054525982eb45d0b7ad95391ebfc1683b8bb0021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5266d6b72dff3bb5c12b92b45b162223eebb7f382a6350f0ae146147bd533f7e 0.600000000000 1544993 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": 1072530, "vin": [ { "gen": { "height": 1072520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5266d6b72dff3bb5c12b92b45b162223eebb7f382a6350f0ae146147bd533f7e" } } ], "extra": [ 1, 125, 120, 215, 107, 151, 228, 58, 162, 183, 119, 206, 48, 148, 208, 84, 82, 89, 130, 235, 69, 208, 183, 173, 149, 57, 30, 191, 193, 104, 59, 139, 176, 2, 17, 0, 0, 0, 7, 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