Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fcde37f1fe49fc75a31de6e234d15c984e8484e438ef13b10f56b71f7eb5918

Tx prefix hash: 8cd686744da8b3723922f80b1937ec8848f35a846f027056dad5b1e6bb3ba47a
Tx public key: d76fa3f8f42771f56ec27061269e23f3b54a3373e2b42a6037a5a44ab278b5de
Timestamp: 1720036484 Timestamp [UCT]: 2024-07-03 19:54:44 Age [y:d:h:m:s]: 00:293:12:02:52
Block: 1057846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209733 RingCT/type: yes/0
Extra: 01d76fa3f8f42771f56ec27061269e23f3b54a3373e2b42a6037a5a44ab278b5de0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c04d602147cb4b4f68a2557d7f8a1a7cc44a992fc44cf46c04c1bc040bd10b49 0.600000000000 1528289 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": 1057856, "vin": [ { "gen": { "height": 1057846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c04d602147cb4b4f68a2557d7f8a1a7cc44a992fc44cf46c04c1bc040bd10b49" } } ], "extra": [ 1, 215, 111, 163, 248, 244, 39, 113, 245, 110, 194, 112, 97, 38, 158, 35, 243, 181, 74, 51, 115, 226, 180, 42, 96, 55, 165, 164, 74, 178, 120, 181, 222, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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