Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feafc8969164e3e81698c88f5e7bb0b30eabc0922dad5f1ecbc876ec23b51be2

Tx prefix hash: 64d63c7fec1ddb29974506768f82dbb4944d9da0d421bfa0f46651da30a499fd
Tx public key: e1f895edef4e77597ea085ed0e575b2eaa008c7ac84aaa182c79a691e5472be3
Timestamp: 1720689948 Timestamp [UCT]: 2024-07-11 09:25:48 Age [y:d:h:m:s]: 00:276:12:35:25
Block: 1063286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197574 RingCT/type: yes/0
Extra: 01e1f895edef4e77597ea085ed0e575b2eaa008c7ac84aaa182c79a691e5472be302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 773bda5d07aeecad287fda5f3f2573e4752c45a02cec292a5e176cba28548ebf 0.600000000000 1533801 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": 1063296, "vin": [ { "gen": { "height": 1063286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "773bda5d07aeecad287fda5f3f2573e4752c45a02cec292a5e176cba28548ebf" } } ], "extra": [ 1, 225, 248, 149, 237, 239, 78, 119, 89, 126, 160, 133, 237, 14, 87, 91, 46, 170, 0, 140, 122, 200, 74, 170, 24, 44, 121, 166, 145, 229, 71, 43, 227, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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