Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b267116a4de41d5692345a67f0d23a2b6d97137128984ae33b932ea29c385a42

Tx prefix hash: 6bb9e70210f90940119d64d221a0a8875c07c8ba2407f821061f0155526b3bfe
Tx public key: ff90c8b0f6e2ac6f6b875066adb9f4722a330828f7cd81f1db1322a1310096c9
Timestamp: 1733035764 Timestamp [UCT]: 2024-12-01 06:49:24 Age [y:d:h:m:s]: 00:114:23:57:55
Block: 1165536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81971 RingCT/type: yes/0
Extra: 01ff90c8b0f6e2ac6f6b875066adb9f4722a330828f7cd81f1db1322a1310096c90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 117e4dd23bca586d5902cf42526c9dd9a34700c3c2e08e68c81679025714fe9c 0.600000000000 1651211 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": 1165546, "vin": [ { "gen": { "height": 1165536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "117e4dd23bca586d5902cf42526c9dd9a34700c3c2e08e68c81679025714fe9c" } } ], "extra": [ 1, 255, 144, 200, 176, 246, 226, 172, 111, 107, 135, 80, 102, 173, 185, 244, 114, 42, 51, 8, 40, 247, 205, 129, 241, 219, 19, 34, 161, 49, 0, 150, 201, 2, 17, 0, 0, 0, 2, 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