Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 866e2ee5dfa273bfd3ecbfe9fa223436f7f64a2eb5b710d53478b735b84d033c

Tx prefix hash: 6861c42efcd0e49c869fd8dbf695fd87f16c6426b6c80a95483c514af014197e
Tx public key: fbbd1fabeb057d93c290302d55688bda081f9895c694b932067a2b6a7f7bf860
Timestamp: 1583346703 Timestamp [UCT]: 2020-03-04 18:31:43 Age [y:d:h:m:s]: 04:267:20:14:39
Block: 76436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1085751 RingCT/type: yes/0
Extra: 01fbbd1fabeb057d93c290302d55688bda081f9895c694b932067a2b6a7f7bf86002110000000356c366d3000000000000000000

1 output(s) for total of 342.559958294000 dcy

stealth address amount amount idx
00: b2cad919800d88f8275e67e3b2fc19847d7ec468e3ca039e52ee5c6e421beb4a 342.559958294000 140691 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": 76446, "vin": [ { "gen": { "height": 76436 } } ], "vout": [ { "amount": 342559958294, "target": { "key": "b2cad919800d88f8275e67e3b2fc19847d7ec468e3ca039e52ee5c6e421beb4a" } } ], "extra": [ 1, 251, 189, 31, 171, 235, 5, 125, 147, 194, 144, 48, 45, 85, 104, 139, 218, 8, 31, 152, 149, 198, 148, 185, 50, 6, 122, 43, 106, 127, 123, 248, 96, 2, 17, 0, 0, 0, 3, 86, 195, 102, 211, 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