Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c40425d7b048d4916850ded73350291299148ea2cc1a91efb041364ec8998ef6

Tx prefix hash: dd6da39354e3ba91b27783465d940925c487cdbdda3f77e58d3c2f2f0fba8fe8
Tx public key: 7c12e6e0daf39d40f8988548d9c4e4a8657156c6d901f06324c3259d13eae3a0
Timestamp: 1579498646 Timestamp [UCT]: 2020-01-20 05:37:26 Age [y:d:h:m:s]: 04:315:19:55:52
Block: 49411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115246 RingCT/type: yes/0
Extra: 017c12e6e0daf39d40f8988548d9c4e4a8657156c6d901f06324c3259d13eae3a002110000002e8a2ee0d9000000000000000000

1 output(s) for total of 420.999596277000 dcy

stealth address amount amount idx
00: b704aa1f038498cf6c781fcc2fdf9dbdce4783c23aa2b3f8281c69f3a62207d7 420.999596277000 91736 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": 49421, "vin": [ { "gen": { "height": 49411 } } ], "vout": [ { "amount": 420999596277, "target": { "key": "b704aa1f038498cf6c781fcc2fdf9dbdce4783c23aa2b3f8281c69f3a62207d7" } } ], "extra": [ 1, 124, 18, 230, 224, 218, 243, 157, 64, 248, 152, 133, 72, 217, 196, 228, 168, 101, 113, 86, 198, 217, 1, 240, 99, 36, 195, 37, 157, 19, 234, 227, 160, 2, 17, 0, 0, 0, 46, 138, 46, 224, 217, 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