Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 657dd9aeb36aee29d6f5619da74879fb2518f0f96c58f0914db2f20245b78498

Tx prefix hash: e679bbc0fa3a991b52336e93d6c1bac98b94e2d83ab803da5e5a2d1f06481ddb
Tx public key: 8a140dfead7ce8167210a61c0c6f86f23273d84038d0b30f0f9d4618fa762271
Timestamp: 1729683129 Timestamp [UCT]: 2024-10-23 11:32:09 Age [y:d:h:m:s]: 00:140:23:26:58
Block: 1137803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100554 RingCT/type: yes/0
Extra: 018a140dfead7ce8167210a61c0c6f86f23273d84038d0b30f0f9d4618fa7622710211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2713428a71bd772ecdeae7577dc4574e23f2bfe5930053f32b2d12c415a543a 0.600000000000 1621364 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": 1137813, "vin": [ { "gen": { "height": 1137803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2713428a71bd772ecdeae7577dc4574e23f2bfe5930053f32b2d12c415a543a" } } ], "extra": [ 1, 138, 20, 13, 254, 173, 124, 232, 22, 114, 16, 166, 28, 12, 111, 134, 242, 50, 115, 216, 64, 56, 208, 179, 15, 15, 157, 70, 24, 250, 118, 34, 113, 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