Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bceb5798d7d30f324ee9b0c15beb3999df72847be8b7c876278f43cb2592ad1

Tx prefix hash: a3672ddc2ead9c5e577579abc60c8cd5f1a14764cd9bd7b6ecd83740366d1ebc
Tx public key: b10decf6e7ed86e72c9669b434fae9f17f41c4057200b87780b0909f406cb0ce
Timestamp: 1729929902 Timestamp [UCT]: 2024-10-26 08:05:02 Age [y:d:h:m:s]: 00:211:03:01:20
Block: 1139851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150722 RingCT/type: yes/0
Extra: 01b10decf6e7ed86e72c9669b434fae9f17f41c4057200b87780b0909f406cb0ce021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9ce599794cefcc2aeec1b8bbd13f052841012b50f9cb10e176fb6728369ee3a 0.600000000000 1623638 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": 1139861, "vin": [ { "gen": { "height": 1139851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9ce599794cefcc2aeec1b8bbd13f052841012b50f9cb10e176fb6728369ee3a" } } ], "extra": [ 1, 177, 13, 236, 246, 231, 237, 134, 231, 44, 150, 105, 180, 52, 250, 233, 241, 127, 65, 196, 5, 114, 0, 184, 119, 128, 176, 144, 159, 64, 108, 176, 206, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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