Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a127c9651a335a090b9c13fe19392c242af5118c9cff54369ad9c312477776e

Tx prefix hash: ff22540ab3b0a2a66f5aa882d2f96609b2a57b5d305b5f097f932cfde9038c2a
Tx public key: 83f1f08fc5890b6433e9683fecbc9062d763986001d38f931f0365b7e2a7104b
Timestamp: 1708147630 Timestamp [UCT]: 2024-02-17 05:27:10 Age [y:d:h:m:s]: 01:035:00:44:46
Block: 959287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286072 RingCT/type: yes/0
Extra: 0183f1f08fc5890b6433e9683fecbc9062d763986001d38f931f0365b7e2a7104b0211000000063f0590f7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9fefd207eb1664f5758dbc6563cbe085a0ceea275486b9edba200b3e7b1b33a 0.600000000000 1418820 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": 959297, "vin": [ { "gen": { "height": 959287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9fefd207eb1664f5758dbc6563cbe085a0ceea275486b9edba200b3e7b1b33a" } } ], "extra": [ 1, 131, 241, 240, 143, 197, 137, 11, 100, 51, 233, 104, 63, 236, 188, 144, 98, 215, 99, 152, 96, 1, 211, 143, 147, 31, 3, 101, 183, 226, 167, 16, 75, 2, 17, 0, 0, 0, 6, 63, 5, 144, 247, 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