Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c22df532fec48273e273c166aa5c404c5fc3ddc8f2607a7974db3459069b6d1

Tx prefix hash: 6c85978e15b6791aaa9b965eab015aa8a8adf18b04cc6069e9bdd6c80e1d23f5
Tx public key: 67d2e747a745e949eb217c5412a3b3fd58e59484d878c6991dedab44eee4cb46
Timestamp: 1719677893 Timestamp [UCT]: 2024-06-29 16:18:13 Age [y:d:h:m:s]: 00:259:17:31:48
Block: 1054882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185591 RingCT/type: yes/0
Extra: 0167d2e747a745e949eb217c5412a3b3fd58e59484d878c6991dedab44eee4cb4602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 856c767bb473305814bbcf94f9ec1d3e614e5537c9c53e5784620b88d86c7728 0.600000000000 1525273 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": 1054892, "vin": [ { "gen": { "height": 1054882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "856c767bb473305814bbcf94f9ec1d3e614e5537c9c53e5784620b88d86c7728" } } ], "extra": [ 1, 103, 210, 231, 71, 167, 69, 233, 73, 235, 33, 124, 84, 18, 163, 179, 253, 88, 229, 148, 132, 216, 120, 198, 153, 29, 237, 171, 68, 238, 228, 203, 70, 2, 17, 0, 0, 0, 3, 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