Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91bbdfe878ff611d0d54a4b8d66d12a3db55e01ce54d5d2f26c47e4ba89980de

Tx prefix hash: ceb20e2186ce94825dd38ef22de662e999de8b258bbc034f3f39861112986166
Tx public key: 275178ae11db2298e6da0c0e4052ceb5af439036944f41dbc2b4ff74d1df1bc0
Timestamp: 1731020456 Timestamp [UCT]: 2024-11-07 23:00:56 Age [y:d:h:m:s]: 01:013:03:03:02
Block: 1148833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267800 RingCT/type: yes/0
Extra: 01275178ae11db2298e6da0c0e4052ceb5af439036944f41dbc2b4ff74d1df1bc00211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0efa34d4e13d87bcdca4bb333689dd9e064c31ae5c3d9a5cb6b1fc38cba927d5 0.600000000000 1633770 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": 1148843, "vin": [ { "gen": { "height": 1148833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0efa34d4e13d87bcdca4bb333689dd9e064c31ae5c3d9a5cb6b1fc38cba927d5" } } ], "extra": [ 1, 39, 81, 120, 174, 17, 219, 34, 152, 230, 218, 12, 14, 64, 82, 206, 181, 175, 67, 144, 54, 148, 79, 65, 219, 194, 180, 255, 116, 209, 223, 27, 192, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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