Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99e2c36de86858198fae7cf26b09bd7e73bf23f0635185502d77c6d17ea09ca8

Tx prefix hash: 03cb2a471f0722e3e042d7c74ff21a7f20577f4810137615294d38d732e71ead
Tx public key: a0a34a724454664ca948d3e6930a3aa1ad82644fe315133e0ed970df6ff70663
Timestamp: 1704563467 Timestamp [UCT]: 2024-01-06 17:51:07 Age [y:d:h:m:s]: 01:305:19:53:55
Block: 929567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477398 RingCT/type: yes/0
Extra: 01a0a34a724454664ca948d3e6930a3aa1ad82644fe315133e0ed970df6ff7066302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3373e6a97620a79d3b9d9ef62a694e91c42e0762cb0544fba9f8e444bd41159 0.600000000000 1387443 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": 929577, "vin": [ { "gen": { "height": 929567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3373e6a97620a79d3b9d9ef62a694e91c42e0762cb0544fba9f8e444bd41159" } } ], "extra": [ 1, 160, 163, 74, 114, 68, 84, 102, 76, 169, 72, 211, 230, 147, 10, 58, 161, 173, 130, 100, 79, 227, 21, 19, 62, 14, 217, 112, 223, 111, 247, 6, 99, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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