Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25d8db57326a17603edef3ceb4279e56a9fae8480121f05b693827bb00165b3f

Tx prefix hash: 8f23fca47d57bbe8dbed1c78e82ab4bc972455e96fd542b41fcbfe46fbaae9ae
Tx public key: 37ead6f1ce65ad5c9452e1f2809bfa2cd55c6fb4e5a289581ef1253e97444706
Timestamp: 1716451300 Timestamp [UCT]: 2024-05-23 08:01:40 Age [y:d:h:m:s]: 01:006:14:02:07
Block: 1028140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265624 RingCT/type: yes/0
Extra: 0137ead6f1ce65ad5c9452e1f2809bfa2cd55c6fb4e5a289581ef1253e9744470602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06b64fabee2df00af22c53e7d264c2c546eac458dd2fc9468b85294ec65b9e96 0.600000000000 1496077 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": 1028150, "vin": [ { "gen": { "height": 1028140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06b64fabee2df00af22c53e7d264c2c546eac458dd2fc9468b85294ec65b9e96" } } ], "extra": [ 1, 55, 234, 214, 241, 206, 101, 173, 92, 148, 82, 225, 242, 128, 155, 250, 44, 213, 92, 111, 180, 229, 162, 137, 88, 30, 241, 37, 62, 151, 68, 71, 6, 2, 17, 0, 0, 0, 2, 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