Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be84fa5fe848dece7a85b100840eb2b1706e210a0236ae45cf46fed38cffbf19

Tx prefix hash: d68453a6f6d0f726b51116e0ead7a68b3fab2422a6ffb5d9a49ab29ab271a76e
Tx public key: 63821c5171318cfc5946af0eb1c8d2c4e19575ad65715fbb25f1a392a880959b
Timestamp: 1706958729 Timestamp [UCT]: 2024-02-03 11:12:09 Age [y:d:h:m:s]: 01:022:23:06:58
Block: 949423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277445 RingCT/type: yes/0
Extra: 0163821c5171318cfc5946af0eb1c8d2c4e19575ad65715fbb25f1a392a880959b02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bed1c9b650c87bd00c1d8f0a43cc520176efc95fbb4f337e4f2e45dcd6606a3 0.600000000000 1407947 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": 949433, "vin": [ { "gen": { "height": 949423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bed1c9b650c87bd00c1d8f0a43cc520176efc95fbb4f337e4f2e45dcd6606a3" } } ], "extra": [ 1, 99, 130, 28, 81, 113, 49, 140, 252, 89, 70, 175, 14, 177, 200, 210, 196, 225, 149, 117, 173, 101, 113, 95, 187, 37, 241, 163, 146, 168, 128, 149, 155, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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