Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 930c4234876ea1b319d5e2fee2a6225bc44913358e9d97aaa05d8f60b97ed51a

Tx prefix hash: 5c744b9270b154f032e3819c3fe556d5b6c30cf8bb155a22015073c52822b0df
Tx public key: ef6b508b45736d80c1d5c2de563c75a32b50af1bb1e2e59402403b6451425ec1
Timestamp: 1735365000 Timestamp [UCT]: 2024-12-28 05:50:00 Age [y:d:h:m:s]: 00:081:16:25:00
Block: 1184807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58190 RingCT/type: yes/0
Extra: 01ef6b508b45736d80c1d5c2de563c75a32b50af1bb1e2e59402403b6451425ec102110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef3eb913933f4a9f0569c71bb99e0a47747d04955d94955fb8876b32610644b9 0.600000000000 1671266 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": 1184817, "vin": [ { "gen": { "height": 1184807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef3eb913933f4a9f0569c71bb99e0a47747d04955d94955fb8876b32610644b9" } } ], "extra": [ 1, 239, 107, 80, 139, 69, 115, 109, 128, 193, 213, 194, 222, 86, 60, 117, 163, 43, 80, 175, 27, 177, 226, 229, 148, 2, 64, 59, 100, 81, 66, 94, 193, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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