Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 949f3b4747d195f859d2e5388afc35a37c46b12fc40ba83efd6fa4b0eb54634f

Tx prefix hash: c73507d2907545d8795ddb8c2d00062fd5a24ea01037c26c57917d12056437b6
Tx public key: dbd5a3fc69ed76994d5a3459b1b43b2f477d3f4e3f8948cf29d013efd3810d8c
Timestamp: 1578161723 Timestamp [UCT]: 2020-01-04 18:15:23 Age [y:d:h:m:s]: 05:132:04:12:04
Block: 38714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244326 RingCT/type: yes/0
Extra: 01dbd5a3fc69ed76994d5a3459b1b43b2f477d3f4e3f8948cf29d013efd3810d8c021100000036bd0f9f9f000000000000000000

1 output(s) for total of 456.807049947000 dcy

stealth address amount amount idx
00: b2b1978598e24465c7f9d1f3b960aa4d488176d243c6f4a4ba554e13fa0aa0ed 456.807049947000 66208 of 0

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": 38724, "vin": [ { "gen": { "height": 38714 } } ], "vout": [ { "amount": 456807049947, "target": { "key": "b2b1978598e24465c7f9d1f3b960aa4d488176d243c6f4a4ba554e13fa0aa0ed" } } ], "extra": [ 1, 219, 213, 163, 252, 105, 237, 118, 153, 77, 90, 52, 89, 177, 180, 59, 47, 71, 125, 63, 78, 63, 137, 72, 207, 41, 208, 19, 239, 211, 129, 13, 140, 2, 17, 0, 0, 0, 54, 189, 15, 159, 159, 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