Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfc33bcdd7017ccc484bc72054d530d009f0c9db2783c7b76d4887c3e4ca9873

Tx prefix hash: e72175548e8e4128cb585d703b2b34068126060fb6147f6f5b8ec68d30c15ab5
Tx public key: 33e447ff746a3501b8b7f929246c47df30933e3b2d9adca473853e4e5cceb972
Timestamp: 1710133753 Timestamp [UCT]: 2024-03-11 05:09:13 Age [y:d:h:m:s]: 01:037:00:45:43
Block: 975770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287461 RingCT/type: yes/0
Extra: 0133e447ff746a3501b8b7f929246c47df30933e3b2d9adca473853e4e5cceb9720211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f256b6e3541658babd88cc3cfc22a4c44d5b17574d92bc040593db071df16d68 0.600000000000 1435745 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": 975780, "vin": [ { "gen": { "height": 975770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f256b6e3541658babd88cc3cfc22a4c44d5b17574d92bc040593db071df16d68" } } ], "extra": [ 1, 51, 228, 71, 255, 116, 106, 53, 1, 184, 183, 249, 41, 36, 108, 71, 223, 48, 147, 62, 59, 45, 154, 220, 164, 115, 133, 62, 78, 92, 206, 185, 114, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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