Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dc8cf12f7b09ffd1365fe8d406b4827b29c36d356104ac390d27b5deb663018

Tx prefix hash: 3dea7fa01f0ec499ff56cd94927fad116022287fbbfc955d4eedfee30b04586b
Tx public key: 9326f5db54af3e651f14d4f7acb6615aebed4c11933c8367bc82f4e2fe4b5cb3
Timestamp: 1708925151 Timestamp [UCT]: 2024-02-26 05:25:51 Age [y:d:h:m:s]: 01:027:09:24:18
Block: 965744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280580 RingCT/type: yes/0
Extra: 019326f5db54af3e651f14d4f7acb6615aebed4c11933c8367bc82f4e2fe4b5cb302110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a2b59f7a9e3ec00131b04447ee5eaf4506f2c7ce920cbb11ea7dbc2b53680d8 0.600000000000 1425499 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": 965754, "vin": [ { "gen": { "height": 965744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a2b59f7a9e3ec00131b04447ee5eaf4506f2c7ce920cbb11ea7dbc2b53680d8" } } ], "extra": [ 1, 147, 38, 245, 219, 84, 175, 62, 101, 31, 20, 212, 247, 172, 182, 97, 90, 235, 237, 76, 17, 147, 60, 131, 103, 188, 130, 244, 226, 254, 75, 92, 179, 2, 17, 0, 0, 0, 9, 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